home *** CD-ROM | disk | FTP | other *** search
- 358665
- 20
- 3
- USER LOGGING ON: @OPTEXT@
- @X08T@X07u@X0Frbo log@X07i@X08n?
- 14
- 123456
- 5
- random
- 9
- 11
- no
- @X0F@LTIME@ @X07@SPD@ @X08@N@ @X07@U/D@ @X08@M@ @X07@ACTS@ @X0F@USERNAME_OR_HANDLE_(USERCITY_OR_AFFILS)@
- LOCAL
- @X0CLEECH
- @X0AELITE
- 9
- No
- Yes
- no
- 15
- @X08φ @X0F
- @X07Submitted by:@X08
- <UNUSED>
- @X08E@X07n@X0Fter a new One Lin@X07e@X08r?
- @X08O@X07n@X0Fe Liner sav@X07e@X08d.
- @X0FWhat are you a moron???(!)?
- %\pcb\ppe\weektop\weektop.pcb
- @X07
- @X1F
- no
-
- ------------SuperLogon----------------------------Another ViG! PPE------------
-
- NOTE: Everything has changed, don't try to use old .CNF file from v1.x.
-
- 1: Registration code. This PPE is not crippled in any way, as
- I think that is extremely lame. All registering does is remove
- the <Unregistered> message when the PPE starts, and now the
- first one liner can finally be changed. :) DON'T make this blank.
-
- 2: Security level needed to access any part of this PPE. If
- a user has anything less than this all features will be
- disabled. NOTE: this does not apply to Slogoff.
-
- 3: (BR)oadcast USER IS LOGGING ON message to all other nodes. Enter the
- number of nodes you run, or 0 if you want to disable this feature or are
- only running 1 node.
-
- 4: Text for option 3. Because of the way the (BR)oadcast function
- works, color is not supported, and everything will be sent in
- CAPS regardless of what you enter here. @OPTEXT@ will be converted
- to the users NAME and NODE NUMBER.
-
- 5: Use TURBO LOGIN feature. Set to "no" to disable, or put the text
- for the prompt as you want it to appear here. If enabled, and the
- user chooses YES, everything will be skipped including any other
- PPE's that you have this one set to call, and the user will be
- dumped at the main menu.
-
- 6: Number of blank lines to output before TURBO LOGIN question. In
- some (most?) cases it will be desirable to have the question
- 'jump over' other text or ansi that is already on the screen,
- experiment with this. (0=no CR's generated, -1=clear screen)
-
- 7: Feature Order. Here you can define the order that each section
- of this PPE will be processed in. 1=welcome screen, 2=user stats,
- 3=last callers, 4=automessage, 5=oneliners, 6=external PPE (option
- #27). You can use each more than once, or omit anything you don't
- want. THIS IS HOW YOU DISABLE FEATURES. JUST OMIT THE NUMBER.
-
- 8: Number of welcome screens to display. You MUST put the welcome
- screens in the same dir as this PPE and you MUST call them
- WELCOME.1 WELCOME.2 WELCOME.3 etc. Make sure they are numbered
- consecutively (and start at WELCOME.1), and make sure you have the
- correct number here.
-
- 9: This decides how to display the WELCOME.xxx screens, either one
- per logon at RANDOM, or ALL of them sequentially. (random|all)
-
- 10:Number of stat screens to randomly display. You MUST put the
- stat screens in the same dir as this PPE and you MUST call them
- STATS.1 STATS.2 STATS.3 etc. Make sure they are numbered
- consecutively (and start at stats.1), and make sure you have the
- correct number here.
-
- 11:Number of most recent callers to track. Easy enough. (25=max)
-
- 12:Log local logons to last callers list AND whether to BRoadcast
- local logons to the other nodes. If you set this to no, any local
- logon by any user name will be omitted from the list and no
- BRoadcast message will be sent. (yes|no)
-
- 13:Caller Order. Here you can define the colors and order that each
- field of info will be displayed in. Substitution codes are as
- follows:
- @LTIME@: Logon Time
- @SPD@ : Connect Speed
- @N@ : Node Number
- @U/D@ : Ul/Dl Ratio
- @M@ : Minutes Online
- @ACTS@ : Actions
- @USERNAME_OR_HANDLE@: Alias/Handle
- @USERCITY_OR_AFFILS@: Location/Group
- @USERNAME_OR_HANDLE_(USERCITY_OR_AFFILS)@: Both together
-
- Any combination will fit. You can use each more than once, or omit
- anything you don't want. Note that the length of the codes are also
- the exact length for that field of data, so you can easily design your
- screen by using PCBEDIT on this file having to worry about formatting
- everything.
-
- 14:Text for Last Callers/Baud Rate when on locally.
-
- 15:Text for Last Callers/Ratio when user is a LEECH.
-
- 16:Text for Last Callers/Ratio when user is a GOOD uler.
-
- 17:Ratio threshold to determine LEECH/GOOD status.
-
- 18:Text for NO in the YES/NO bars
-
- 19:Text for YES in the YES/NO bars
-
- 20:Default for TURBO LOGON question, YES or NO
-
- 21:Number of oneliners to keep before the bottom one is removed.
- (25=max)
-
- 22:Bullet color and character to put in front of each one liner.
- If you put more than 3 chars here (that aren't part of a color
- code), one liners may wrap. The last color code will be the
- default color of the oneliner, of course any color codes the
- users put in will override this.
-
- 23:The string and or colors preceding the author's name of each one
- liner, displayed only if they have sysop security. You should
- keep it indented for clarity when viewing SUBMITTED BY's.
-
- 24:<UNUSED>
-
- 25:Prompt color and text shown after the one liners are displayed, asking
- if they would like to add a new one.
-
- 26:Color and text shown to user to let him (her?) know their one
- liner has been saved.
-
- 27:MORON string :) Shown if the user says YES i want to add
- a one liner, but then hits ENTER without any input.
-
- 28:Drive:path\filename.xxx of another PPE you would like to execute
- or file to display. Precede with an '!' or '%' as appropriate.
-
- 29:Color for UNLIT choice in YES/NO bars.
-
- 30:Color for LIT choice in YES/NO bars.
-
- 31:Default for ADD ONELINER question, YES or NO
-
-